-
Notifications
You must be signed in to change notification settings - Fork 172
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable traditional threading as an option #3149
base: develop
Are you sure you want to change the base?
Enable traditional threading as an option #3149
Conversation
After some waiting for WW3 points, it seems the model progressed in the test on Hercules. The run will time out at 30 mins, because I was testing it. Still worth taking a look at the log. |
A run of the test C768_S2SW succeeded on Hercules with traditional threading. |
@JessicaMeixner-NOAA is there an expectation the model reproduces results based on who is managing threading? |
I would think that we should get the same answers regardless of if it's ESMF managed threading or not, or how many threads. I don't know if ufs-weather-model currently tests, but assume that was probably an early test if not a current one. |
CI Passed on Hera in Build# 1
|
Description
In a previous PR, stubs were added to enable traditional threading in the UFS.
This PR takes the next step to execute the model with traditional threading.
Specifically;
_esmf
ufs_configure
file for traditional threading. This sets theglobalResourceControl
tofalse
(traditional threading) ... this was done in the previous PRufs_configure
... this PRexport OMP_NUM_THREADS=$UFS_THREADS
... this was done in the previous PRThe default behaviour to use ESMF-managed threading is retained. Traditional threading can be achieved by toggling
USE_ESMF_THREADING
flag inconfig.fcst
Closes #3122 - as in allows the model to be configured to run w/ traditional threading. Testing on C768 S2SW was successful on Hercules (This was previously reported to be failing)
The use of traditional threading will be inefficient for model components that are not thread-enabled and supported e.g. MOM6 and CICE6, but since they require smaller number of tasks compared to ATM or WAV, the CPU 'waste' is not huge.
Type of change
Change characteristics
How has this been tested?
Testing on Hercules for a C768 S2SW case was run with traditional threading (4 threads)
Some particulars of the run are as follows:
Run directory:
/work/noaa/stmp/rmahajan/HERCULES/RUNDIRS/c768s2swtt/gfs.2019120300/gfsfcst.2019120300/fcst.2077795/
Run log:
/work2/noaa/stmp/rmahajan/RUNTESTS//COMROOT/c768s2swtt/logs/2019120300/gfs_fcst_seg0.log
Checklist